home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group00b.txt
/
000056_icon-group-sender _Fri Sep 22 16:43:16 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2001-01-03
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id QAA03787
for icon-group-addresses; Fri, 22 Sep 2000 16:42:51 -0700 (MST)
Message-Id: <200009222342.QAA03787@baskerville.CS.Arizona.EDU>
To: "Charles Hethcoat" <CHETHCOA@oss.oceaneering.com>
Cc: icon-group@optima.CS.Arizona.EDU, suzdal@altavista.net
Subject: Re: parse stack overflow
Date: Fri, 22 Sep 2000 14:54:41 -0700
From: Clinton L Jeffery <jeffery@big-bill.CS.UNLV.EDU>
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 945
Recently suzdal@altavista.net wrote of parse stack overflows in his big
program. I will take a crack at providing a better answer than I have
heard so far.
Very old versions of Icont have a number of static limits built-in to them
that could be raised, within certain bounds, using command-line options. If
the command-line options can't be raised high enough for your large program,
the best options are to (a) move to a newer version of Icon, or (b) break
your program into more, smaller procedures. There are sometimes other
extreme measures that can be taken, but if either (a) or (b) works for you
they are your best option. The static compiler limits were gone by Icon
Version 9, and maybe gone by Icon Version 8, someone else could say for sure
on that. Suzdal, I would be surprised if there is not a newer version of
Mac Icon available to you than what you are currently using.
Cheers, and good luck!
Clint jeffery@cs.unlv.edu